fix: add TrackerDB Utilities category
#1892
Conversation
| @@ -40,6 +41,7 @@ export const order = [ | |||
| 'site_analytics', | |||
| 'consent', | |||
| 'essential', | |||
There was a problem hiding this comment.
I would keep it for two reasons:
- When the extension independently gets rolled out on different platforms, there will be still TrackerDB with "essential" (because updating TrackerDB before will reintroduce the production problem from last time)
- TrackerPreview will update independently with a delay as well (coupled to the monthly WhoTracks.me data release)
In other words, the clients needs to support utilities, but remain backward compatible to the current TrackerDB state until the changes fully propagated through the system and all platforms are running with the latest extension code.
Unfortunately, is not possible with our current infrastructure. Once TrackerDB is modified, it will propagate to production. That means, first releasing the update here to all platforms and then updating TrackerDB is what I would suggest. |
|
I manually changed the name to |
Fixes #1885
utilitiescategory, which replaces theessentialessential, as the TrackerDB must be updated when all of the platforms update to the version with the change@philipp-classen We should clean up the
essentialcategory once we update. Please create an issue, when you will update the TrackerDB.Also, it would be great to push the "changed" TrackerDB to the staging CDN, so we can test the change.